-
Notifications
You must be signed in to change notification settings - Fork 530
distroless-iptables: remove dependency from conntrack binary #4223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
distroless-iptables: remove dependency from conntrack binary #4223
Conversation
|
Following up from #3726, |
cpanato
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/hold for @BenTheElder to comment
| mkdir -p "${STAGE_DIR}" && \ | ||
| /stage-binaries-from-package.sh "${STAGE_DIR}" conntrack \ | ||
| ebtables \ | ||
| /stage-binaries-from-package.sh "${STAGE_DIR}" ebtables \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
now that I see this, I think ebtables was only required for some dockershim kubelet stuff, @danwinship to keep me honest
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, kubernetes/kubernetes#28717. Definitely not needed any more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aroradaman can you please remove the ebtables, that is not likely going to be used anywhere , howeve, regarding the conntrack binary this image is used in another projects too https://grep.app/search?q=distroless-iptables ... I'm unclear on what contract do we have with this image or what are the expectactions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The README says "Serves as the base image for registry.k8s.io/kube-proxy-${ARCH}." I don't think we ever implied that we supported random projects using it as a base image.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, as a maintainer of one of those images, if we needed something missing from this image that would be our problem.
In upstream, kubernetes/dns probably isn't using conntrack, and kindnetd just needs ... iptables.
The rest of these appear to be references to Kubernetes/Kubernetes releases and this image itself (e.g. the build job)
https://cs.k8s.io/?q=distroless-iptables&i=nope&literal=nope&files=&excludeFiles=&repos=
BenTheElder
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aroradaman, BenTheElder, cpanato The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
needs a rebase after the ebtables cleanup |
Signed-off-by: Daman Arora <aroradaman@gmail.com>
a9a97a0 to
76e09ce
Compare
BenTheElder
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
LGTM |
|
/hold cancel |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
With kubernetes/kubernetes#126847 kube-proxy will no longer depend on
conntrackbinary to be present on the image, this PR removes the conntrack binary from the distroless-iptables image.Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?